home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-03-06 | 1.6 KB | 40 lines | [TEXT/GEOL] |
- Item 4894766 16-Feb-88 18:25
-
- From: BIANCHI1 Bianchi, Curt
-
- To: D1002 PEMD Ed Group, Dev, E Rosenberg
-
- cc: MACAPP$ MacApp Interest List
-
- Sub: Response to Compiler Version…
-
- Ernie,
-
- I can think of a couple of possibilities that would explain different behavior
- between a debug and non-debug (or optimized) MacApp program.
-
- One thing to do is to determine if you get the same behavior when you build
- "nondebug" as when you build "opt." Both options strip out debugging code from
- your program. Opt goes a step further and optimizes the method calls.
-
- If your program runs find with "nondebug" but bombs with "opt" then it could be
- the fault of the MPW linker, which had a fairly obscure bug that caused some
- optimized programs to fail. I'm not sure whether the fixed linker is generally
- available, but Harvey Alcabes (ALCABES1) should be able to tell you.
-
- If your program fails with "nondebug" then you may have a problem with
- uninitialized data. One difference between a debug and non-debug program is
- that the debug program initializes global variables, local variables, and
- function results to the hex pattern 7267. Furthermore, all objects are
- initialized with the hex pattern 3F21. In non-debug this initialization
- doesn't take place. The upshot of this is that it causes some uninitialized
- data problems to appear in debug programs, while others don't crop up until the
- non-debug program is run. If your program runs fine in debug, but not in
- non-debug then this may be the problem.
-
- Hope this helps.
-
- Curt Bianchi
- Apple Computer
-
-